our custom formatter).

      Note that this parser cannot be used with Ohloh because it does
      not emit the SHA1 hash of modified blobs.

      This is sort of a hack, caused by using git-whatchanged to
      generate our git logs.

      Long-term, we should try to get away from git-whatchanged, but I
      couldn't find a combination of options to git-log that would
      provide the needed blob SHA1s for all of the changed files.

…resses.

      If a directory is renamed, and then the branch we are tracking
      is created within that directory *during the same commit*, then
      the parser would mistakenly think that the branch had been moved.

…acters

      New implementation requires only 2 shell commands (rather than 3).

Add the --include-merges flag to the `bzr log` command.
Old bzr 1.12 included merges by default; the upgrade requires the flag.

It is possible for Bzr to report that a file has been renamed
and then modified in a single commit.

This breaks Ohloh, because a 'modify' action triggers a
comparison between the old and new files -- but since this file
has also been renamed, the old file does not exist (at least not
where Ohloh expects it).

We adapt the Bazaar system to what Ohloh expects: A rename
becomes a simple delete and add, and any subsequent modification
is ignored.

Hg now sometimes returns a trailing "+" character after a revid.
We need to strip this away.

doing svn info on missing files. Existing code, e.g. deepen_diff(),
relies on this returning an empty result with a success code.

Resolves http://thechaw.com/ohloh_scm/tickets/view/19

Parse the author name as well as the committer name
from the Bzr log.

Add a guard to restrict_url_to_trunk() so that it will
not do any work if the URL already ends with /trunk

During production operation, we always force users to specify
a module name. During test our tests, we are using an empty string
as the module name.

CVSNT has varying behavior when the module name is left empty.
In some builds (Mac development machines), leaving out the module
name causes rlog to include the CVSROOT directory, while in other
builds (production machines) the CVSROOT directory is excluded.

The presence or absence of the CVSROOT directory causes a unit test
to pass or fail with different cvsnt builds.

The flaw here is in the test harness: it should not leave the module
name empty, and thus the CVSROOT directory should never be logged.

I have modified the test harness to specify the CVS module name
everywhere. I have modified the expected responses from CVS to
exclude the CVSROOT directory.

This is a backport of Ohloh commit a2d86034. It has been live in
production since Nov 2009, but was never applied to the lib/scm
repository.

This is a backport of Ohloh commit f9b0c4be, ticket OTWO-16.

This is a backport of Ohloh commit fa1c6f7d, OTWO-55

Backport of Ohloh commit 4341cd0c.

Rolls back 6851c5c and applies alternate fix. Unit tests now pass.

Increment ohloh_scm version to 2.2.9

OTWO-4616 Fetch SVN tags in xml format

OTWO-4616 Update version to 2.2.10

OTWO-4616 Make dependency on nokogiri to not be overly strict

OTWO-4616 Add test case for fetching svn tags with whitespaces

OTWO-4722 Implement Export Tag Method for Bzr Repo

[OTWO-4428] SVN fix: Import commits earlier than replace commit

OTWO: 4721 Raise an exception if repository is empty

OTWO-4738 Upgrade Ruby in Ohloh SCM to 2.2

…stead of short

OTWO=4901: Changed Hg adapter commit head_token to return long sha in…

OTWO-4904: Fix error caused due branch_name set to nil